Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1185

reference: 887-tree-1
name: 1185
tree-preservation-order: undefined
887-tpo-1
uprn
address-text
point: POINT (-1.017605 50.879138)
geometry: MULTIPOLYGON (((-1.017548 50.879131,-1.017551 50.879143,-1.017559 50.879153,-1.017571 50.879161,-1.017587 50.879166,-1.017605 50.879168,-1.017622 50.879166,-1.017638 50.879161,-1.017651 50.879153,-1.017659 50.879144,-1.017662 50.879132,-1.017660 50.879121,-1.017652 50.879111,-1.017639 50.879103,-1.017624 50.879098,-1.017606 50.879096,-1.017588 50.879098,-1.017572 50.879103,-1.017560 50.879110,-1.017551 50.879120,-1.017548 50.879131)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL